Restrict Users From Baselining?

Hello. I have modules in my database that require the preservation of object history content. Certain tools that I use examine this history information. I want to disallow users from being able to baseline certain modules (and therby prevent users from removing the history information from the current baseline). Is this possible and if so how? Thank you very much.
SystemAdmin - Thu Feb 10 16:34:04 EST 2011

Re: Restrict Users From Baselining?
Mathias Mamsch - Thu Feb 10 16:55:35 EST 2011

As long as they are in exclusive edit and have RMC rights on the module they can baseline the module. I guess the only thing you could try is a) revoke the module create access and remove inheritance from the top level objects in the module granting the users access again. The other possibility would be to b) force the user by a trigger to work in shared edit mode. But the disadvantages of both approaches are so massive (like not being able to create top level objects, access rights not inherited, when changed on the module/folder, the module history growing and growing making the module very slow over time, etc. ), that I would like to ask if it would not be better if you made the object history available to your tools over several baselines. I am pretty sure that one can come up with an include library that will allow you to only change only one line in your tools and make them read the history entries for all baselines. Example:

Instead of writing:

History h 
 
    for h in obj do { 
      ... 
    }

You could make a nice library and replace the calls with:

History h 
    for h in BaselineHistory obj do {
    ...
    }

All you would need to do is a function BaselineHistory that will do some intelligent caching and return a Skip list containing the history records from several baselines or something like that.

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Restrict Users From Baselining?
SystemAdmin - Thu Feb 10 18:46:16 EST 2011